Systems and methods for generating, providing, and rendering quick load articles

ABSTRACT

Systems, methods, and non-transitory computer-readable media can transmit a quick load article request identifying a quick load article. One or more media content elements associated with the quick load article are received, the one or more media content elements comprising a first quick load embedded web content element. The first quick load embedded web content element comprises embedded web content element information identifying a first embedded web content element and snapshot information identifying a first snapshot associated with the first embedded web content element. The quick load article is rendered, wherein the rendering the quick load article comprises rendering the first snapshot in place of the first embedded web content element.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/165,958, filed on May 26, 2016 and entitled “SYSTEMS AND METHODS FORGENERATING, PROVIDING, AND RENDERING QUICK LOAD ARTICLES”, which isincorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present technology relates to the field of social networks. Moreparticularly, the present technology relates to generation, provision,and rendering of quick load articles.

BACKGROUND

Today, people often utilize computing devices (or systems) for a widevariety of purposes. Users can use their computing devices, for example,to interact with one another, create content, share content, and viewcontent. In some cases, a user can utilize his or her computing deviceto access a social networking system (or service). The user can provide,post, share, and access various content items, such as status updates,images, videos, articles, and links, via the social networking system.

Users of a social networking system can be given the opportunity tointeract with media content items posted to the social networking systemby other users. For example, users can share and/or view articles on thesocial networking system. Articles can be posted directly to the socialnetworking system. Alternatively, articles can be shared from externalsources. For example, a user can share a link to an online articlepublished by a newspaper or other publication. A user can view, commenton, share, or otherwise interact with articles posted by other users. Byimproving a user's experience with sharing and viewing articles on thesocial networking system, a user's experience with the social networkingsystem as a whole can be improved.

SUMMARY

Various embodiments of the present disclosure can include systems,methods, and non-transitory computer readable media configured totransmit a quick load article request identifying a quick load article.One or more media content elements associated with the quick loadarticle are received, the one or more media content elements comprisinga first quick load embedded web content element. The first quick loadembedded web content element comprises embedded web content elementinformation identifying a first embedded web content element andsnapshot information identifying a first snapshot associated with thefirst embedded web content element. The quick load article is rendered,wherein the rendering the quick load article comprises rendering thefirst snapshot in place of the first embedded web content element.

In an embodiment, the rendering the quick load article further comprisesreplacing the first snapshot with the first embedded web content elementonce the first embedded web content element has completed loading.

In an embodiment, the first snapshot has been selected from a pluralityof snapshots associated with the first embedded web content element.

In an embodiment, the quick load article request comprises mobile deviceinformation.

In an embodiment, the first snapshot was selected from the plurality ofsnapshots based on the mobile device information.

In an embodiment, the mobile device information comprises screendimension information.

In an embodiment, the mobile device information comprises screen densityinformation.

In an embodiment, the plurality of snapshots comprise a plurality ofimage dimensions and image resolutions.

In an embodiment, the snapshot information comprises snapshot dimensioninformation.

In an embodiment, the snapshot information comprises snapshot resolutioninformation.

It should be appreciated that many other features, applications,embodiments, and/or variations of the disclosed technology will beapparent from the accompanying drawings and from the following detaileddescription. Additional and/or alternative implementations of thestructures, systems, non-transitory computer readable media, and methodsdescribed herein can be employed without departing from the principlesof the disclosed technology.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system including a quick load articlemodule, according to an embodiment of the present disclosure.

FIG. 2 illustrates an example quick load article generation module,according to an embodiment of the present disclosure.

FIG. 3 illustrates an example quick load article display module,according to an embodiment of the present disclosure.

FIG. 4A illustrates an example method for creating a quick load article,according to an embodiment of the present disclosure.

FIG. 4B illustrates an example method for rendering a quick loadarticle, according to an embodiment of the present disclosure.

FIG. 5 illustrates an example scenario of a server side and a clientside exchanging information, according to an embodiment of the presentdisclosure.

FIG. 6 illustrates a network diagram of an example system including anexample social networking system that can be utilized in variousscenarios, according to an embodiment of the present disclosure.

FIG. 7 illustrates an example of a computer system or computing devicethat can be utilized in various scenarios, according to an embodiment ofthe present disclosure.

The figures depict various embodiments of the disclosed technology forpurposes of illustration only, wherein the figures use like referencenumerals to identify like elements. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated in the figures can be employedwithout departing from the principles of the disclosed technologydescribed herein.

DETAILED DESCRIPTION Quick Load Article Generation and Display

People use computing devices (or systems) for a wide variety ofpurposes. Computing devices can provide different kinds offunctionality. Users can utilize their computing devices to produceinformation, access information, and share information. In some cases,users can utilize computing devices to interact or engage with aconventional social networking system (i.e., a social networkingservice, a social network, etc.). For example, users can add friends orcontacts, provide, post, or publish content items, such as text, notes,status updates, links, pictures, videos, and audio, via the socialnetworking system.

Users of a social networking system can be given the opportunity tointeract with media content items posted to the social networking systemby other users. For example, users can share and/or view articles on thesocial networking system. Articles can be posted directly to the socialnetworking system. Alternatively, articles can be shared from externalsources. For example, a user can share a link to an online articlepublished by a newspaper or other publication. A user can view, commenton, share, or otherwise interact with articles posted by other users. Byimproving a user's experience with sharing and viewing articles on thesocial networking system, a user's experience with the social networkingsystem as a whole can be improved.

It continues to be an important interest for a social networking systemto improve the user experience of users sharing and viewing content onthe social networking system. Continued user interaction with contentposted to the social networking is an important aspect of maintainingcontinued interest in and participation on the social networking system.However, articles can contain numerous embedded web content elementswhich may take a long time to load and disrupt user experience inviewing such articles. This is particularly true today, when articlescan contain lots of embedded web content from other sources, e.g.,Twitter, YouTube, Instagram, etc. These embedded web content elementsare included in articles to increase user interest, but if such embeddedweb content elements cause negative user experiences, users may loseinterest in viewing an article, or be dissuaded from viewing futurearticles. One example of negative user experience caused by embedded webcontent elements can include long load times, and blank spaces inarticles where embedded web content elements have not yet loaded. Inanother example, embedded web content elements can cause slow framerates, resulting in uneven scrolling through an article due to excessivememory consumption by embedded web content elements. In yet anotherexample, embedded web content elements can cause article layoutrestructuring disruptions, which can occur when a user begins reading anarticle before all embedded web content elements have loaded. As theembedded web content elements load, they can push other media contentelements to different positions to fit the loaded embedded web contentelements, causing the user's view to be disrupted as text or images orother elements are repositioned.

An improved approach rooted in computer technology overcomes theforegoing and other disadvantages associated with conventionalapproaches specifically arising in the realm of computer technology.Based on computer technology, the disclosed technology can receive anarticle, and parse the article into different media content elements.For example, an article can be parsed into one or more text elements,one or more image elements, one or more video elements, and/or one ormore embedded web content elements. Any media content elements that arein a format that can be rendered natively by a social networkapplication or other browser application can be stored and rendered inthat format. For example, text elements, image elements, and/or videoelements can be stored in one or more formats that can be renderednatively by a social network application. For other media contentelements that cannot be rendered natively, such as embedded web contentelements, the disclosed technology can render an embedded web contentelement on a mobile device, and take an image, or snapshot, of therendered embedded web content element. The snapshot can be saved as animage that can be rendered natively by the social network application.The article can be saved as a quick load article by creating quick loadembedded web content elements, which comprise both embedded web contentelement information identifying an embedded web content element, andsnapshot information identifying snapshots associated with the embeddedweb content element. When a later user requests a quick load article,for example, by clicking on a link on a social networking feed, thequick load article can load with one or more snapshots in the place ofany embedded web content elements. The snapshots can be loadedrelatively quickly and efficiently, whereas embedded web content itemsmay take a long time to load and negatively affect user experience. Inthis way, the user is provided with an improved viewing experience, asthe user can quickly see snapshots representing each embedded webcontent element, rather than a blank space while the embedded webcontent element is loading. Furthermore, additional benefits may beprovided. For example, quick load articles can have an improved framerate when a user scrolls through because snapshots require less memorythan embedded web content, and quick load articles can result in fewerlayout restructuring disruptions caused by slowly loading embedded webcontent elements.

FIG. 1 illustrates an example system 100 including an example quick loadarticle module 102 configured to generate and display quick loadarticles, according to an embodiment of the present disclosure. Thequick load article module 102 can be configured to receive an article,and parse the article into different media content elements. Forexample, an article can be parsed into one or more text elements, one ormore image elements, one or more video elements, and/or one or moreembedded web content elements. For a given article, the quick loadarticle module 102 can be configured to compile a list of embedded webcontent elements. The list of embedded web content elements can betransmitted to one or more mobile devices for rendering of each embeddedweb content element. Each embedded web content element of the list ofembedded web content elements can be rendered on one or more mobiledevices. Once an embedded web content element is rendered on a mobiledevice, a snapshot of the rendered embedded web content element can betaken and stored. Each embedded web content element can be convertedinto a quick load embedded web content element by adding snapshotinformation identifying one or more snapshots associated with theembedded web content element. As such, quick load embedded web contentelements comprise embedded web content element information, identifyingan embedded web content element, and snapshot information, identifyingone or more snapshots associated with the embedded web content element.A quick load article can be created by storing the one or more mediacontent elements of the article, with one or more embedded web contentelements replaced by quick load embedded web content elements. When alater user requests the quick load article, for example, by clicking ona link on a social networking feed, the quick load article can load withone or more snapshots in the place of embedded web content elements.

As shown in the example of FIG. 1, the quick load article module 102 caninclude a quick load article generation module 104 and a quick loadarticle display module 106. In some instances, the example system 100can include at least one data store 112. The components (e.g., modules,elements, etc.) shown in this figure and all figures herein areexemplary only, and other implementations may include additional, fewer,integrated, or different components. Some components may not be shown soas not to obscure relevant details.

The quick load article generation module 104 can be configured toreceive an article and generate a quick load article based on thearticle. In certain embodiments, the quick load article generationmodule 104 can be configured to receive an article in an HTML format.The article can be parsed for one or more media content elements thatmake up the article. For example, the article can be parsed into one ormore text elements, one or more image elements, one or more videoelements, and/or one or more embedded web content elements. The quickload article generation module 104 can be configured to compile a listof all embedded web content elements in the article. The list ofembedded web content elements can be transmitted to one or more mobiledevices for rendering of each embedded web content element. In certainembodiments, the list of embedded web content elements can betransmitted to a data center comprising one or more mobile devices. Eachembedded web content element can be rendered on the one or more mobiledevices, or a subset of the one or more mobile devices, and one or moresnapshots of each rendered embedded web content element can be taken,creating snapshot image versions of the rendered embedded web contentelement. The one or more snapshots can be stored for future use.Although many of the examples and descriptions disclosed herein willmake reference to interacting with mobile devices, it should beunderstood that the disclosed technology can also be applied tonon-mobile computing devices, such as desktop or laptop computers. Anembedded web content element can be converted to a quick load embeddedweb content element by appending snapshot information identifying one ormore snapshots associated with the embedded web content element. Forexample, the snapshot information can include one or more URLsidentifying locations of the one or more snapshots. The plurality ofmedia content elements that make up the article can be stored as a quickload article by converting any embedded web content elements into quickload embedded web content elements. The quick load article generationmodule 104 is discussed in greater detail herein.

The quick load article display module 106 can be configured to display aquick load article on a mobile device. In certain embodiments, the quickload article display module 106 can transmit a quick load articlerequest, requesting rendering of a quick load article. For example, thisrequest may be sent by a social networking application on a user'smobile device in response to a user clicking on a link associated withthe quick load article. The quick load article display module 106 canreceive one or more media content elements associated with the quickload article to the mobile device for rendering on the mobile device.The one or more media content elements can contain one or more quickload embedded web content elements. Each quick load embedded web contentelement can contain embedded web content element information identifyingan embedded web content element, and snapshot information identifyingone or more snapshots associated with the embedded web content element,as discussed above. As each embedded web content element can beassociated with more than one snapshot, a mobile device appropriatesnapshot can be selected from the snapshots for use with a particularmobile device. The mobile device appropriate snapshot can be selectedbased on mobile device characteristics of the mobile device. Forexample, the mobile device characteristics can comprise screen sizeinformation, and screen density information. When a quick load embeddedweb content element is transmitted to the mobile device, the quick loadembedded web content element can include the mobile device appropriatesnapshot itself, or the snapshot information included in the quick loadembedded web content element can identify an address (e.g., URL) for themobile device to retrieve the mobile device appropriate snapshot. Whenthe article is rendered on the mobile device, the mobile deviceappropriate snapshot can be displayed in place of the embedded webcontent element. In certain embodiments, the mobile device appropriatesnapshot can be displayed while the embedded web content is loading, andthen be replaced by the embedded web content once it has finishedloading. The quick load article display module 106 is discussed ingreater detail herein.

The quick load article module 102 can be implemented, in part or inwhole, as software, hardware, or any combination thereof. In general, amodule as discussed herein can be associated with software, hardware, orany combination thereof. In some implementations, one or more functions,tasks, and/or operations of modules can be carried out or performed bysoftware routines, software processes, hardware, and/or any combinationthereof. In some cases, the quick load article module 102 can beimplemented, in part or in whole, as software running on one or morecomputing devices or systems, such as on a server computing system or auser (or client) computing system. For example, the quick load articlemodule 102 or at least a portion thereof can be implemented as or withinan application (e.g., app), a program, or an applet, etc., running on auser computing device or a client computing system, such as the userdevice 610 of FIG. 6. In another example, the quick load article module102 or at least a portion thereof can be implemented using one or morecomputing devices or systems that include one or more servers, such asnetwork servers or cloud servers. In some instances, the quick loadarticle module 102 can, in part or in whole, be implemented within orconfigured to operate in conjunction with a social networking system (orservice), such as the social networking system 630 of FIG. 6. It shouldbe understood that there can be many variations or other possibilities.

The quick load article module 102 can be configured to communicateand/or operate with the at least one data store 112, as shown in theexample system 100. The data store 112 can be configured to store andmaintain various types of data. In some implementations, the data store112 can store information associated with the social networking system(e.g., the social networking system 630 of FIG. 6). The informationassociated with the social networking system can include data aboutusers, user identifiers, social connections, social interactions,profile information, demographic information, locations, geo-fencedareas, maps, places, events, pages, groups, posts, communications,content, feeds, account settings, privacy settings, a social graph, andvarious other types of data. In some embodiments, the data store 112 canstore information that is utilized by the quick load article module 102.For example, the data store 112 can store article information, mediacontent element information, a plurality of snapshots, mobile deviceinformation, and the like. It is contemplated that there can be manyvariations or other possibilities.

FIG. 2 illustrates an example quick load article generation module 202configured to generate quick load articles, according to an embodimentof the present disclosure. In some embodiments, the quick load articlegeneration module 104 of FIG. 1 can be implemented as the example quickload article generation module 202. As shown in FIG. 2, the quick loadarticle generation module 202 can include an article parsing module 204and a snapshot generation module 206.

The article parsing module 204 can be configured to receive an article,and parse the article into one or more media content elements. Forexample, if an article comprises a first text section, followed by afirst image, followed by a second text section, followed by a firstembedded web content item (e.g., a tweet, or an Instagram image),followed by a third section of text, the article can be parsed into afirst text element, a first image element, a second text element, afirst embedded web content element, and a third text element. In certainembodiments, as will be described in greater detail below, each embeddedweb content element can be converted into a quick load embedded webcontent element by appending snapshot information identifying one ormore snapshots associated with the embedded web content element. Incertain embodiments, the article parsing module 204 can be configured togenerate a list of embedded web content elements in an article, and totransmit the list of embedded web content elements to the snapshotgeneration module 206 for generation of snapshots.

The snapshot generation module 206 can be configured to generate one ormore snapshots for one or more embedded web content elements. In certainembodiments, the snapshot generation module 206 receives a list ofembedded web content elements identifying one or more embedded webcontent elements. Each embedded web content element in the list ofembedded web content elements can be identified, for example, by a URLand/or HTML. Once the snapshot generation module 206 receives the listof embedded web content elements, the snapshot generation module 206renders a first embedded web content element of the list of embedded webcontent elements on one or more mobile devices. Once the first embeddedweb content element is rendered, a snapshot is taken of the renderedembedded web content element, creating an image version of the embeddedweb content element. In certain embodiments, an embedded web contentelement can be rendered on a plurality of mobile devices, each of theplurality of mobile devices having different screen characteristics. Forexample, each mobile device can have a different screen size or screenwidth, such that a plurality of snapshots having different dimensionsare taken of the first embedded web content element. In certainembodiments, each mobile device can take multiple snapshots at differentresolutions, such that for each screen size, multiple snapshots havingdifferent resolutions are taken. Each embedded web content element inthe list of embedded web content elements is loaded on the plurality ofmobile devices, and snapshots of each embedded web content element aretaken and stored. Once the snapshot generation module 206 has workedthrough the entire list of embedded web content elements, each embeddedweb content element has a plurality of snapshots of varying dimensionsand varying resolutions associated with it. Each embedded web contentelement can be modified into a quick load embedded web content element,wherein the quick load embedded web content element includes embeddedweb content element information (e.g., a URL and/or HTML identifying theembedded web content element) and snapshot information identifying theplurality of snapshots associated with the embedded web content element.Snapshot information can include URLs for each of the plurality ofsnapshots, and dimension and resolution information for each of theplurality of snapshots. A quick load article comprises the one or moremedia content elements of an article, with any embedded web contentelements in the article converted into quick load embedded web contentelements, i.e., by appending snapshot information.

FIG. 3 illustrates an example quick load article display module 302configured to render a quick load article, according to an embodiment ofthe present disclosure. In some embodiments, the quick load articledisplay module 106 of FIG. 1 can be implemented as the example quickload article display module 302. As shown in FIG. 3, the quick loadarticle display module 302 can include a quick load article retrievalmodule 304, a snapshot retrieval module 306, and a quick load articlerendering module 308.

The quick load article retrieval module 304 can be configured totransmit a quick load article request, requesting a quick load articlefor rendering on a user's mobile device. For example, if a user isbrowsing a social networking system feed via a social networkapplication on the user's mobile device, and clicks on a link to view aquick load article, the quick load article retrieval module 304 cantransmit a quick load article request requesting the quick load article.The quick load article retrieval module 304 receives one or more mediacontent elements associated with the requested quick load article. Theone or more media content elements can include one or more quick loadembedded web content elements. While the quick load article retrievalmodule 304 and various other modules disclosed herein may be discussedfrom a particular vantage point, it should be appreciated that oppositeor complementary vantage points also fall within the scope of thepresent disclosure. For example, whereas the quick load articleretrieval module 304 has been described as transmitting a quick loadarticle request and receiving one or more media content elementsassociated with a quick load article, a complementary quick load articleretrieval module can be configured to receive the quick load articlerequest, and transmit the one or more media content elements associatedwith the quick load article to a mobile device.

The snapshot retrieval module 306 can be configured to identify a mobiledevice appropriate snapshot based on an embedded web content element,and mobile device information. As discussed above, an embedded webcontent element can be associated with a plurality of snapshots, eachsnapshot having particular dimensions (e.g., screen width) andresolution. When the quick load article retrieval module 304 requests aquick load article, the quick load article request can include mobiledevice information identifying various mobile device displaycharacteristics of the mobile device. For example, the mobile deviceinformation can identify the screen width and screen density (orresolution) of the mobile device. Alternatively, the mobile deviceinformation can identify a particular mobile device model, from whichthe screen width and screen density can be inferred. Based on the mobiledevice information, a mobile device appropriate snapshot is selectedfrom the plurality of snapshots associated with the embedded web contentelement. For example, if a mobile device has a screen width of 1080 anda density of 400, a mobile device appropriate snapshot can be selectedthat most closely matches the screen width and density of the mobiledevice.

The quick load article rendering module 308 can be configured to rendera quick load article on a user mobile device. The quick load articlerendering module 308 can receive one or more media content elements fromthe quick load article retrieval module 304, and render each of themedia content elements to display a quick load article. When the quickload article retrieval module 304 transmits the one or more mediacontent elements to the quick load article rendering module 308, eachquick load embedded web content element can comprise snapshotinformation identifying the mobile device appropriate snapshot selectedfor each embedded web content element. In this way, a mobile deviceappropriate snapshot for each embedded web content element can beretrieved and rendered in place of each embedded web content element.Snapshot information can include a URL or address associated with themobile device appropriate snapshot, a width, a height, and a resolution(or scale) of the mobile device appropriate snapshot, and the like. Byrendering a snapshot in place of an embedded web content element, auser's viewing experience can be improved for various reasons. Forexample, it will typically be the case that the rendering of a snapshotwill take place much more quickly than loading and rendering an embeddedweb content element, so the user is presented with the visual elementsof a quick load article more quickly than if the user had to wait foreach embedded web content element to load. Furthermore, snapshots areimages, which generally consume fewer resources than embedded webcontent elements, thereby improving computing performance and frame rateas a user scrolls through the quick load article. Additionally, embeddedweb content elements can cause shifting or repositioning of other mediacontent elements (such as text surrounding an embedded web contentelement) as the embedded web content element loads. A snapshot loadedquickly in place of an embedded web content element quickly sets thedimensions of the embedded web content article so that even once anembedded web content element loads, it simply replaces the spaceoccupied by the snapshot and does not require shifting or repositioningof other media content elements. In certain embodiments, a snapshot canbe permanently displayed in a quick load article in place of an embeddedweb content element. In other embodiments, a snapshot can be displayedin place of an embedded web content element while the embedded webcontent element loads, and then be replaced by the embedded web contentelement once loading is completed.

FIG. 4A illustrates an example method 400 associated with creating aquick load article, according to an embodiment of the presentdisclosure. It should be appreciated that there can be additional,fewer, or alternative steps performed in similar or alternative orders,or in parallel, based on the various features and embodiments discussedherein unless otherwise stated.

At block 402, the example method 400 can receive an article. At block404, the example method 400 can parse the article into one or more mediacontent elements, the one or more media content elements comprising afirst embedded web content element. At block 406, the example method 400can render the first embedded web content element on a first mobiledevice. At block 408, the example method 400 can take a first snapshotof the first embedded web content element rendered on the first mobiledevice. At block 410, the example method 400 can create a first quickload embedded web content element based on the first embedded webcontent element and the first snapshot. At block 412, the example method400 can create a quick load article comprising the first quick loadembedded web content element. Other suitable techniques that incorporatevarious features and embodiments of the present technology are possible.

FIG. 4B illustrates an example method 450 associated with rendering aquick load article, according to an embodiment of the presentdisclosure. It should be appreciated that there can be additional,fewer, or alternative steps performed in similar or alternative orders,or in parallel, based on the various features and embodiments discussedherein unless otherwise stated.

At block 452, the example method 450 can transmit a quick load articlerequest identifying a quick load article. At block 454, the examplemethod 450 can receive one or more media content elements associatedwith the quick load article, the one or more media content elementscomprising a first quick load embedded web content element, the firstquick load embedded web content element comprising embedded web contentelement information identifying a first embedded web content element,and snapshot information identifying a first snapshot associated withthe first embedded web content element. At block 456, the example method450 can render the quick load article, wherein the rendering the quickload article comprises rendering the first snapshot in place of thefirst embedded web content element. Other suitable techniques thatincorporate various features and embodiments of the present technologyare possible.

FIG. 5 illustrates an example scenario 500 in which a server side 510and a client side 550 exchange information, according to an embodimentof the present disclosure. At block 512, the server side 510 receives anarticle and parses it into one or more media content elements. The oneor more media content elements include one or more embedded web contentelements. At block 514, the server side 510 generates snapshots of allembedded web content elements in the article, as discussed in greaterdetail above. At block 516, the article is converted into a quick loadarticle by converting each embedded web content element in the articleinto a quick load embedded web content element. Each quick load embeddedweb content element comprises embedded web content element information,identifying an embedded web content element, and snapshot information,identifying one or more snapshots associated with the embedded webcontent element.

At block 552, the client side 550 transmits a quick load article requestto the server side 510. The server side 510 receives the quick loadarticle request at block 518. The quick load article request mightoccur, for example, as a result of a user clicking on a link on theuser's mobile device to open a quick load article. In certainembodiments, the quick load article request includes mobile deviceinformation. At block 520, the server side 510 determines mobile deviceappropriate snapshots for each quick load embedded web content elementbased on the mobile device information. In certain embodiments,determining a mobile device appropriate snapshot can include selectingfrom a plurality of snapshots a snapshot that best matches mobile devicedisplay characteristics of the user's mobile device. At block 522, mediacontent elements associated with the quick load article (including quickload embedded web content elements and snapshot information identifyingone or more snapshots for each quick load embedded web content element)are transmitted to the client side 550, which receives the media contentelements at block 554. At block 556, the client side 550 renders thequick load article 556. In certain embodiments, rendering the quick loadarticle 556 comprises rendering snapshots in place of embedded webcontent elements. For example, if a mobile device appropriate snapshothas been selected for each quick load embedded web content element, themobile device appropriate snapshot can be rendered in place of eachembedded web content element.

Although various blocks have been described as being associated with aserver side 510 or a client side 550, it should be appreciated thatvarious features may be implemented differently while still remainingwithin the scope of the present disclosure. For example, the client sidemay be provided with snapshot information for all snapshots associatedwith each quick load embedded web content element, and the client sidemay be tasked with determining mobile device appropriate snapshots basedon mobile device information.

Social Networking System—Example Implementation

FIG. 6 illustrates a network diagram of an example system 600 that canbe utilized in various scenarios, according to an embodiment of thepresent disclosure. The system 600 includes one or more user devices610, one or more external systems 620, a social networking system (orservice) 630, and a network 650. In an embodiment, the social networkingservice, provider, and/or system discussed in connection with theembodiments described above may be implemented as the social networkingsystem 630. For purposes of illustration, the embodiment of the system600, shown by FIG. 6, includes a single external system 620 and a singleuser device 610. However, in other embodiments, the system 600 mayinclude more user devices 610 and/or more external systems 620. Incertain embodiments, the social networking system 630 is operated by asocial network provider, whereas the external systems 620 are separatefrom the social networking system 630 in that they may be operated bydifferent entities. In various embodiments, however, the socialnetworking system 630 and the external systems 620 operate inconjunction to provide social networking services to users (or members)of the social networking system 630. In this sense, the socialnetworking system 630 provides a platform or backbone, which othersystems, such as external systems 620, may use to provide socialnetworking services and functionalities to users across the Internet.

The user device 610 comprises one or more computing devices that canreceive input from a user and transmit and receive data via the network650. In one embodiment, the user device 610 is a conventional computersystem executing, for example, a Microsoft Windows compatible operatingsystem (OS), Apple OS X, and/or a Linux distribution. In anotherembodiment, the user device 610 can be a device having computerfunctionality, such as a smart-phone, a tablet, a personal digitalassistant (PDA), a mobile telephone, etc. The user device 610 isconfigured to communicate via the network 650. The user device 610 canexecute an application, for example, a browser application that allows auser of the user device 610 to interact with the social networkingsystem 630. In another embodiment, the user device 610 interacts withthe social networking system 630 through an application programminginterface (API) provided by the native operating system of the userdevice 610, such as iOS and ANDROID. The user device 610 is configuredto communicate with the external system 620 and the social networkingsystem 630 via the network 650, which may comprise any combination oflocal area and/or wide area networks, using wired and/or wirelesscommunication systems.

In one embodiment, the network 650 uses standard communicationstechnologies and protocols. Thus, the network 650 can include linksusing technologies such as Ethernet, 802.11, worldwide interoperabilityfor microwave access (WiMAX), 3G, 4G, CDMA, GSM, LTE, digital subscriberline (DSL), etc. Similarly, the networking protocols used on the network650 can include multiprotocol label switching (MPLS), transmissioncontrol protocol/Internet protocol (TCP/IP), User Datagram Protocol(UDP), hypertext transport protocol (HTTP), simple mail transferprotocol (SMTP), file transfer protocol (FTP), and the like. The dataexchanged over the network 650 can be represented using technologiesand/or formats including hypertext markup language (HTML) and extensiblemarkup language (XML). In addition, all or some links can be encryptedusing conventional encryption technologies such as secure sockets layer(SSL), transport layer security (TLS), and Internet Protocol security(IPsec).

In one embodiment, the user device 610 may display content from theexternal system 620 and/or from the social networking system 630 byprocessing a markup language document 614 received from the externalsystem 620 and from the social networking system 630 using a browserapplication 612. The markup language document 614 identifies content andone or more instructions describing formatting or presentation of thecontent. By executing the instructions included in the markup languagedocument 614, the browser application 612 displays the identifiedcontent using the format or presentation described by the markuplanguage document 614. For example, the markup language document 614includes instructions for generating and displaying a web page havingmultiple frames that include text and/or image data retrieved from theexternal system 620 and the social networking system 630. In variousembodiments, the markup language document 614 comprises a data fileincluding extensible markup language (XML) data, extensible hypertextmarkup language (XHTML) data, or other markup language data.Additionally, the markup language document 614 may include JavaScriptObject Notation (JSON) data, JSON with padding (JSONP), and JavaScriptdata to facilitate data-interchange between the external system 620 andthe user device 610. The browser application 612 on the user device 610may use a JavaScript compiler to decode the markup language document614.

The markup language document 614 may also include, or link to,applications or application frameworks such as FLASH™ or Unity™applications, the SilverLight™ application framework, etc.

In one embodiment, the user device 610 also includes one or more cookies616 including data indicating whether a user of the user device 610 islogged into the social networking system 630, which may enablemodification of the data communicated from the social networking system630 to the user device 610.

The external system 620 includes one or more web servers that includeone or more web pages 622 a, 622 b, which are communicated to the userdevice 610 using the network 650. The external system 620 is separatefrom the social networking system 630. For example, the external system620 is associated with a first domain, while the social networkingsystem 630 is associated with a separate social networking domain. Webpages 622 a, 622 b, included in the external system 620, comprise markuplanguage documents 614 identifying content and including instructionsspecifying formatting or presentation of the identified content.

The social networking system 630 includes one or more computing devicesfor a social network, including a plurality of users, and providingusers of the social network with the ability to communicate and interactwith other users of the social network. In some instances, the socialnetwork can be represented by a graph, i.e., a data structure includingedges and nodes. Other data structures can also be used to represent thesocial network, including but not limited to databases, objects,classes, meta elements, files, or any other data structure. The socialnetworking system 630 may be administered, managed, or controlled by anoperator. The operator of the social networking system 630 may be ahuman being, an automated application, or a series of applications formanaging content, regulating policies, and collecting usage metricswithin the social networking system 630. Any type of operator may beused.

Users may join the social networking system 630 and then add connectionsto any number of other users of the social networking system 630 to whomthey desire to be connected. As used herein, the term “friend” refers toany other user of the social networking system 630 to whom a user hasformed a connection, association, or relationship via the socialnetworking system 630. For example, in an embodiment, if users in thesocial networking system 630 are represented as nodes in the socialgraph, the term “friend” can refer to an edge formed between anddirectly connecting two user nodes.

Connections may be added explicitly by a user or may be automaticallycreated by the social networking system 630 based on commoncharacteristics of the users (e.g., users who are alumni of the sameeducational institution). For example, a first user specifically selectsa particular other user to be a friend. Connections in the socialnetworking system 630 are usually in both directions, but need not be,so the terms “user” and “friend” depend on the frame of reference.Connections between users of the social networking system 630 areusually bilateral (“two-way”), or “mutual,” but connections may also beunilateral, or “one-way.” For example, if Bob and Joe are both users ofthe social networking system 630 and connected to each other, Bob andJoe are each other's connections. If, on the other hand, Bob wishes toconnect to Joe to view data communicated to the social networking system630 by Joe, but Joe does not wish to form a mutual connection, aunilateral connection may be established. The connection between usersmay be a direct connection; however, some embodiments of the socialnetworking system 630 allow the connection to be indirect via one ormore levels of connections or degrees of separation.

In addition to establishing and maintaining connections between usersand allowing interactions between users, the social networking system630 provides users with the ability to take actions on various types ofitems supported by the social networking system 630. These items mayinclude groups or networks (i.e., social networks of people, entities,and concepts) to which users of the social networking system 630 maybelong, events or calendar entries in which a user might be interested,computer-based applications that a user may use via the socialnetworking system 630, transactions that allow users to buy or sellitems via services provided by or through the social networking system630, and interactions with advertisements that a user may perform on oroff the social networking system 630. These are just a few examples ofthe items upon which a user may act on the social networking system 630,and many others are possible. A user may interact with anything that iscapable of being represented in the social networking system 630 or inthe external system 620, separate from the social networking system 630,or coupled to the social networking system 630 via the network 650.

The social networking system 630 is also capable of linking a variety ofentities. For example, the social networking system 630 enables users tointeract with each other as well as external systems 620 or otherentities through an API, a web service, or other communication channels.The social networking system 630 generates and maintains the “socialgraph” comprising a plurality of nodes interconnected by a plurality ofedges. Each node in the social graph may represent an entity that canact on another node and/or that can be acted on by another node. Thesocial graph may include various types of nodes. Examples of types ofnodes include users, non-person entities, content items, web pages,groups, activities, messages, concepts, and any other things that can berepresented by an object in the social networking system 630. An edgebetween two nodes in the social graph may represent a particular kind ofconnection, or association, between the two nodes, which may result fromnode relationships or from an action that was performed by one of thenodes on the other node. In some cases, the edges between nodes can beweighted. The weight of an edge can represent an attribute associatedwith the edge, such as a strength of the connection or associationbetween nodes. Different types of edges can be provided with differentweights. For example, an edge created when one user “likes” another usermay be given one weight, while an edge created when a user befriendsanother user may be given a different weight.

As an example, when a first user identifies a second user as a friend,an edge in the social graph is generated connecting a node representingthe first user and a second node representing the second user. Asvarious nodes relate or interact with each other, the social networkingsystem 630 modifies edges connecting the various nodes to reflect therelationships and interactions.

The social networking system 630 also includes user-generated content,which enhances a user's interactions with the social networking system630. User-generated content may include anything a user can add, upload,send, or “post” to the social networking system 630. For example, a usercommunicates posts to the social networking system 630 from a userdevice 610. Posts may include data such as status updates or othertextual data, location information, images such as photos, videos,links, music or other similar data and/or media. Content may also beadded to the social networking system 630 by a third party. Content“items” are represented as objects in the social networking system 630.In this way, users of the social networking system 630 are encouraged tocommunicate with each other by posting text and content items of varioustypes of media through various communication channels. Suchcommunication increases the interaction of users with each other andincreases the frequency with which users interact with the socialnetworking system 630.

The social networking system 630 includes a web server 632, an APIrequest server 634, a user profile store 636, a connection store 638, anaction logger 640, an activity log 642, and an authorization server 644.In an embodiment of the invention, the social networking system 630 mayinclude additional, fewer, or different components for variousapplications. Other components, such as network interfaces, securitymechanisms, load balancers, failover servers, management and networkoperations consoles, and the like are not shown so as to not obscure thedetails of the system.

The user profile store 636 maintains information about user accounts,including biographic, demographic, and other types of descriptiveinformation, such as work experience, educational history, hobbies orpreferences, location, and the like that has been declared by users orinferred by the social networking system 630. This information is storedin the user profile store 636 such that each user is uniquelyidentified. The social networking system 630 also stores data describingone or more connections between different users in the connection store638. The connection information may indicate users who have similar orcommon work experience, group memberships, hobbies, or educationalhistory. Additionally, the social networking system 630 includesuser-defined connections between different users, allowing users tospecify their relationships with other users. For example, user-definedconnections allow users to generate relationships with other users thatparallel the users' real-life relationships, such as friends,co-workers, partners, and so forth. Users may select from predefinedtypes of connections, or define their own connection types as needed.Connections with other nodes in the social networking system 630, suchas non-person entities, buckets, cluster centers, images, interests,pages, external systems, concepts, and the like are also stored in theconnection store 638.

The social networking system 630 maintains data about objects with whicha user may interact. To maintain this data, the user profile store 636and the connection store 638 store instances of the corresponding typeof objects maintained by the social networking system 630. Each objecttype has information fields that are suitable for storing informationappropriate to the type of object. For example, the user profile store636 contains data structures with fields suitable for describing auser's account and information related to a user's account. When a newobject of a particular type is created, the social networking system 630initializes a new data structure of the corresponding type, assigns aunique object identifier to it, and begins to add data to the object asneeded. This might occur, for example, when a user becomes a user of thesocial networking system 630, the social networking system 630 generatesa new instance of a user profile in the user profile store 636, assignsa unique identifier to the user account, and begins to populate thefields of the user account with information provided by the user.

The connection store 638 includes data structures suitable fordescribing a user's connections to other users, connections to externalsystems 620 or connections to other entities. The connection store 638may also associate a connection type with a user's connections, whichmay be used in conjunction with the user's privacy setting to regulateaccess to information about the user. In an embodiment of the invention,the user profile store 636 and the connection store 638 may beimplemented as a federated database.

Data stored in the connection store 638, the user profile store 636, andthe activity log 642 enables the social networking system 630 togenerate the social graph that uses nodes to identify various objectsand edges connecting nodes to identify relationships between differentobjects. For example, if a first user establishes a connection with asecond user in the social networking system 630, user accounts of thefirst user and the second user from the user profile store 636 may actas nodes in the social graph. The connection between the first user andthe second user stored by the connection store 638 is an edge betweenthe nodes associated with the first user and the second user. Continuingthis example, the second user may then send the first user a messagewithin the social networking system 630. The action of sending themessage, which may be stored, is another edge between the two nodes inthe social graph representing the first user and the second user.Additionally, the message itself may be identified and included in thesocial graph as another node connected to the nodes representing thefirst user and the second user.

In another example, a first user may tag a second user in an image thatis maintained by the social networking system 630 (or, alternatively, inan image maintained by another system outside of the social networkingsystem 630). The image may itself be represented as a node in the socialnetworking system 630. This tagging action may create edges between thefirst user and the second user as well as create an edge between each ofthe users and the image, which is also a node in the social graph. Inyet another example, if a user confirms attending an event, the user andthe event are nodes obtained from the user profile store 636, where theattendance of the event is an edge between the nodes that may beretrieved from the activity log 642. By generating and maintaining thesocial graph, the social networking system 630 includes data describingmany different types of objects and the interactions and connectionsamong those objects, providing a rich source of socially relevantinformation.

The web server 632 links the social networking system 630 to one or moreuser devices 610 and/or one or more external systems 620 via the network650. The web server 632 serves web pages, as well as other web-relatedcontent, such as Java, JavaScript, Flash, XML, and so forth. The webserver 632 may include a mail server or other messaging functionalityfor receiving and routing messages between the social networking system630 and one or more user devices 610. The messages can be instantmessages, queued messages (e.g., email), text and SMS messages, or anyother suitable messaging format.

The API request server 634 allows one or more external systems 620 anduser devices 610 to call access information from the social networkingsystem 630 by calling one or more API functions. The API request server634 may also allow external systems 620 to send information to thesocial networking system 630 by calling APIs. The external system 620,in one embodiment, sends an API request to the social networking system630 via the network 650, and the API request server 634 receives the APIrequest. The API request server 634 processes the request by calling anAPI associated with the API request to generate an appropriate response,which the API request server 634 communicates to the external system 620via the network 650. For example, responsive to an API request, the APIrequest server 634 collects data associated with a user, such as theuser's connections that have logged into the external system 620, andcommunicates the collected data to the external system 620. In anotherembodiment, the user device 610 communicates with the social networkingsystem 630 via APIs in the same manner as external systems 620.

The action logger 640 is capable of receiving communications from theweb server 632 about user actions on and/or off the social networkingsystem 630. The action logger 640 populates the activity log 642 withinformation about user actions, enabling the social networking system630 to discover various actions taken by its users within the socialnetworking system 630 and outside of the social networking system 630.Any action that a particular user takes with respect to another node onthe social networking system 630 may be associated with each user'saccount, through information maintained in the activity log 642 or in asimilar database or other data repository. Examples of actions taken bya user within the social networking system 630 that are identified andstored may include, for example, adding a connection to another user,sending a message to another user, reading a message from another user,viewing content associated with another user, attending an event postedby another user, posting an image, attempting to post an image, or otheractions interacting with another user or another object. When a usertakes an action within the social networking system 630, the action isrecorded in the activity log 642. In one embodiment, the socialnetworking system 630 maintains the activity log 642 as a database ofentries. When an action is taken within the social networking system630, an entry for the action is added to the activity log 642. Theactivity log 642 may be referred to as an action log.

Additionally, user actions may be associated with concepts and actionsthat occur within an entity outside of the social networking system 630,such as an external system 620 that is separate from the socialnetworking system 630. For example, the action logger 640 may receivedata describing a user's interaction with an external system 620 fromthe web server 632. In this example, the external system 620 reports auser's interaction according to structured actions and objects in thesocial graph.

Other examples of actions where a user interacts with an external system620 include a user expressing an interest in an external system 620 oranother entity, a user posting a comment to the social networking system630 that discusses an external system 620 or a web page 622 a within theexternal system 620, a user posting to the social networking system 630a Uniform Resource Locator (URL) or other identifier associated with anexternal system 620, a user attending an event associated with anexternal system 620, or any other action by a user that is related to anexternal system 620. Thus, the activity log 642 may include actionsdescribing interactions between a user of the social networking system630 and an external system 620 that is separate from the socialnetworking system 630.

The authorization server 644 enforces one or more privacy settings ofthe users of the social networking system 630. A privacy setting of auser determines how particular information associated with a user can beshared. The privacy setting comprises the specification of particularinformation associated with a user and the specification of the entityor entities with whom the information can be shared. Examples ofentities with which information can be shared may include other users,applications, external systems 620, or any entity that can potentiallyaccess the information. The information that can be shared by a usercomprises user account information, such as profile photos, phonenumbers associated with the user, user's connections, actions taken bythe user such as adding a connection, changing user profile information,and the like.

The privacy setting specification may be provided at different levels ofgranularity. For example, the privacy setting may identify specificinformation to be shared with other users; the privacy settingidentifies a work phone number or a specific set of related information,such as, personal information including profile photo, home phonenumber, and status. Alternatively, the privacy setting may apply to allthe information associated with the user. The specification of the setof entities that can access particular information can also be specifiedat various levels of granularity. Various sets of entities with whichinformation can be shared may include, for example, all friends of theuser, all friends of friends, all applications, or all external systems620. One embodiment allows the specification of the set of entities tocomprise an enumeration of entities. For example, the user may provide alist of external systems 620 that are allowed to access certaininformation. Another embodiment allows the specification to comprise aset of entities along with exceptions that are not allowed to access theinformation. For example, a user may allow all external systems 620 toaccess the user's work information, but specify a list of externalsystems 620 that are not allowed to access the work information. Certainembodiments call the list of exceptions that are not allowed to accesscertain information a “block list”. External systems 620 belonging to ablock list specified by a user are blocked from accessing theinformation specified in the privacy setting. Various combinations ofgranularity of specification of information, and granularity ofspecification of entities, with which information is shared arepossible. For example, all personal information may be shared withfriends whereas all work information may be shared with friends offriends.

The authorization server 644 contains logic to determine if certaininformation associated with a user can be accessed by a user's friends,external systems 620, and/or other applications and entities. Theexternal system 620 may need authorization from the authorization server644 to access the user's more private and sensitive information, such asthe user's work phone number. Based on the user's privacy settings, theauthorization server 644 determines if another user, the external system620, an application, or another entity is allowed to access informationassociated with the user, including information about actions taken bythe user.

In some embodiments, the social networking system 630 can include aquick load article module 646. The quick load article module 646 can,for example, be implemented as the quick load article module 102, asdiscussed in more detail herein. As discussed previously, it should beappreciated that there can be many variations or other possibilities.For example, in some embodiments, one or more functionalities of thequick load article module 646 can be implemented in the user device 610.

Hardware Implementation

The foregoing processes and features can be implemented by a widevariety of machine and computer system architectures and in a widevariety of network and computing environments. FIG. 7 illustrates anexample of a computer system 700 that may be used to implement one ormore of the embodiments described herein according to an embodiment ofthe invention. The computer system 700 includes sets of instructions forcausing the computer system 700 to perform the processes and featuresdiscussed herein. The computer system 700 may be connected (e.g.,networked) to other machines. In a networked deployment, the computersystem 700 may operate in the capacity of a server machine or a clientmachine in a client-server network environment, or as a peer machine ina peer-to-peer (or distributed) network environment. In an embodiment ofthe invention, the computer system 700 may be the social networkingsystem 630, the user device 610, and the external system 620, or acomponent thereof. In an embodiment of the invention, the computersystem 700 may be one server among many that constitutes all or part ofthe social networking system 630.

The computer system 700 includes a processor 702, a cache 704, and oneor more executable modules and drivers, stored on a computer-readablemedium, directed to the processes and features described herein.Additionally, the computer system 700 includes a high performanceinput/output (I/O) bus 706 and a standard I/O bus 708. A host bridge 710couples processor 702 to high performance I/O bus 706, whereas I/O busbridge 712 couples the two buses 706 and 708 to each other. A systemmemory 714 and one or more network interfaces 716 couple to highperformance I/O bus 706. The computer system 700 may further includevideo memory and a display device coupled to the video memory (notshown). Mass storage 718 and I/O ports 720 couple to the standard I/Obus 708. The computer system 700 may optionally include a keyboard andpointing device, a display device, or other input/output devices (notshown) coupled to the standard I/O bus 708. Collectively, these elementsare intended to represent a broad category of computer hardware systems,including but not limited to computer systems based on thex86-compatible processors manufactured by Intel Corporation of SantaClara, Calif., and the x86-compatible processors manufactured byAdvanced Micro Devices (AMD), Inc., of Sunnyvale, Calif., as well as anyother suitable processor.

An operating system manages and controls the operation of the computersystem 700, including the input and output of data to and from softwareapplications (not shown). The operating system provides an interfacebetween the software applications being executed on the system and thehardware components of the system. Any suitable operating system may beused, such as the LINUX Operating System, the Apple Macintosh OperatingSystem, available from Apple Computer Inc. of Cupertino, Calif., UNIXoperating systems, Microsoft® Windows® operating systems, BSD operatingsystems, and the like. Other implementations are possible.

The elements of the computer system 700 are described in greater detailbelow. In particular, the network interface 716 provides communicationbetween the computer system 700 and any of a wide range of networks,such as an Ethernet (e.g., IEEE 802.3) network, a backplane, etc. Themass storage 718 provides permanent storage for the data and programminginstructions to perform the above-described processes and featuresimplemented by the respective computing systems identified above,whereas the system memory 714 (e.g., DRAM) provides temporary storagefor the data and programming instructions when executed by the processor702. The I/O ports 720 may be one or more serial and/or parallelcommunication ports that provide communication between additionalperipheral devices, which may be coupled to the computer system 700.

The computer system 700 may include a variety of system architectures,and various components of the computer system 700 may be rearranged. Forexample, the cache 704 may be on-chip with processor 702. Alternatively,the cache 704 and the processor 702 may be packed together as a“processor module”, with processor 702 being referred to as the“processor core”. Furthermore, certain embodiments of the invention mayneither require nor include all of the above components. For example,peripheral devices coupled to the standard I/O bus 708 may couple to thehigh performance I/O bus 706. In addition, in some embodiments, only asingle bus may exist, with the components of the computer system 700being coupled to the single bus. Moreover, the computer system 700 mayinclude additional components, such as additional processors, storagedevices, or memories.

In general, the processes and features described herein may beimplemented as part of an operating system or a specific application,component, program, object, module, or series of instructions referredto as “programs”. For example, one or more programs may be used toexecute specific processes described herein. The programs typicallycomprise one or more instructions in various memory and storage devicesin the computer system 700 that, when read and executed by one or moreprocessors, cause the computer system 700 to perform operations toexecute the processes and features described herein. The processes andfeatures described herein may be implemented in software, firmware,hardware (e.g., an application specific integrated circuit), or anycombination thereof.

In one implementation, the processes and features described herein areimplemented as a series of executable modules run by the computer system700, individually or collectively in a distributed computingenvironment. The foregoing modules may be realized by hardware,executable modules stored on a computer-readable medium (ormachine-readable medium), or a combination of both. For example, themodules may comprise a plurality or series of instructions to beexecuted by a processor in a hardware system, such as the processor 702.Initially, the series of instructions may be stored on a storage device,such as the mass storage 718. However, the series of instructions can bestored on any suitable computer readable storage medium. Furthermore,the series of instructions need not be stored locally, and could bereceived from a remote storage device, such as a server on a network,via the network interface 716. The instructions are copied from thestorage device, such as the mass storage 718, into the system memory 714and then accessed and executed by the processor 702. In variousimplementations, a module or modules can be executed by a processor ormultiple processors in one or multiple locations, such as multipleservers in a parallel processing environment.

Examples of computer-readable media include, but are not limited to,recordable type media such as volatile and non-volatile memory devices;solid state memories; floppy and other removable disks; hard diskdrives; magnetic media; optical disks (e.g., Compact Disk Read-OnlyMemory (CD ROMS), Digital Versatile Disks (DVDs)); other similarnon-transitory (or transitory), tangible (or non-tangible) storagemedium; or any type of medium suitable for storing, encoding, orcarrying a series of instructions for execution by the computer system700 to perform any one or more of the processes and features describedherein.

For purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the description. It will beapparent, however, to one skilled in the art that embodiments of thedisclosure can be practiced without these specific details. In someinstances, modules, structures, processes, features, and devices areshown in block diagram form in order to avoid obscuring the description.In other instances, functional block diagrams and flow diagrams areshown to represent data and logic flows. The components of blockdiagrams and flow diagrams (e.g., modules, blocks, structures, devices,features, etc.) may be variously combined, separated, removed,reordered, and replaced in a manner other than as expressly describedand depicted herein.

Reference in this specification to “one embodiment”, “an embodiment”,“other embodiments”, “one series of embodiments”, “some embodiments”,“various embodiments”, or the like means that a particular feature,design, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the disclosure. Theappearances of, for example, the phrase “in one embodiment” or “in anembodiment” in various places in the specification are not necessarilyall referring to the same embodiment, nor are separate or alternativeembodiments mutually exclusive of other embodiments. Moreover, whetheror not there is express reference to an “embodiment” or the like,various features are described, which may be variously combined andincluded in some embodiments, but also variously omitted in otherembodiments. Similarly, various features are described that may bepreferences or requirements for some embodiments, but not otherembodiments.

The language used herein has been principally selected for readabilityand instructional purposes, and it may not have been selected todelineate or circumscribe the inventive subject matter. It is thereforeintended that the scope of the invention be limited not by this detaileddescription, but rather by any claims that issue on an application basedhereon. Accordingly, the disclosure of the embodiments of the inventionis intended to be illustrative, but not limiting, of the scope of theinvention, which is set forth in the following claims.

What is claimed is:
 1. A computer-implemented method comprising:generating, by a computing system, a quick load article comprising aquick load embedded web content element, wherein the quick load embeddedweb content element comprises: embedded web content element informationidentifying an embedded web content element, and snapshot informationidentifying a snapshot associated with the embedded web content element;and providing, by the computing system, the quick load article, whereinthe quick load article allows for the snapshot to render within thequick load article in place of the embedded web content element.
 2. Thecomputer-implemented method of claim 1, further comprising: parsing, bythe computing system, an article comprising media content elements,wherein the media content elements comprise the embedded web contentelement; and wherein generating the quick load article is based in parton the article.
 3. The computer-implemented method of claim 2, whereinthe media content elements further comprise a text element, an imageelement, or a video element.
 4. The computer-implemented method of claim2, wherein the embedded web content element is included in a pluralityof embedded web content elements and wherein the quick load articlecomprises a plurality of quick load embedded web content elementsassociated with the plurality of embedded web content elements.
 5. Thecomputer-implemented method of claim 4, wherein the quick load articleallows for a plurality of snapshots to render within the quick loadarticle in place of the plurality of embedded web content elements. 6.The computer-implemented method of claim 1, wherein the snapshotassociated with the embedded web content element is an image of theembedded web content element rendered on a mobile device.
 7. Thecomputer-implemented method of claim 6, wherein the snapshot is includedin a plurality of snapshots associated with the embedded web contentelement.
 8. The computer-implemented method of claim 7, wherein theplurality of snapshots is a plurality of images of the web contentelement rendered on a plurality of mobile devices associated with aplurality of screen dimensions or screen resolutions.
 9. Thecomputer-implemented method of claim 8, wherein the quick load articleis provided in response to a quick load article request comprisingmobile device information, screen dimension information, or screenresolution information.
 10. The computer-implemented method of claim 9,wherein the snapshot associated with the embedded web content element isselected from the plurality of snapshots based in part on the mobiledevice information, the screen dimension information, or the screenresolution information.
 11. A system comprising: at least one processor;and a memory storing instructions that, when executed by the at leastone processor, cause the system to perform a method comprising:generating a quick load article comprising a quick load embedded webcontent element, wherein the quick load embedded web content elementcomprises: embedded web content element information identifying anembedded web content element, and snapshot information identifying asnapshot associated with the embedded web content element; and providingthe quick load article, wherein the quick load article allows for thesnapshot to render within the quick load article in place of theembedded web content element.
 12. The system of claim 11, furthercomprising: parsing an article comprising media content elements,wherein the media content elements comprise the embedded web contentelement; and wherein generating the quick load article is based in parton the article.
 13. The system of claim 12, wherein the media contentelements further comprise a text element, an image element, or a videoelement.
 14. The system of claim 12, wherein the embedded web contentelement is included in a plurality of embedded web content elements andwherein the quick load article comprises a plurality of quick loadembedded web content elements associated with the plurality of embeddedweb content elements.
 15. The system of claim 14, wherein the quick loadarticle allows for a plurality of snapshots to render within the quickload article in place of the plurality of embedded web content elements.16. A non-transitory computer-readable storage medium includinginstructions that, when executed by at least one processor of acomputing system, cause the computing system to perform a methodcomprising: generating a quick load article comprising a quick loadembedded web content element, wherein the quick load embedded webcontent element comprises: embedded web content element informationidentifying an embedded web content element, and snapshot informationidentifying a snapshot associated with the embedded web content element;and providing the quick load article, wherein the quick load articleallows for the snapshot to render within the quick load article in placeof the embedded web content element.
 17. The non-transitorycomputer-readable storage medium of claim 16, further comprising:parsing an article comprising media content elements, wherein the mediacontent elements comprise the embedded web content element; and whereingenerating the quick load article is based in part on the article. 18.The non-transitory computer-readable storage medium of claim 17, whereinthe media content elements further comprise a text element, an imageelement, or a video element.
 19. The non-transitory computer-readablestorage medium of claim 17, wherein the embedded web content element isincluded in a plurality of embedded web content elements and wherein thequick load article comprises a plurality of quick load embedded webcontent elements associated with the plurality of embedded web contentelements.
 20. The non-transitory computer-readable storage medium ofclaim 19, wherein the quick load article allows for a plurality ofsnapshots to render within the quick load article in place of theplurality of embedded web content elements.